home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d23
/
bbzipc.arc
/
READ.ME
< prev
next >
Wrap
Text File
|
1989-02-07
|
2KB
|
52 lines
IMPORTANT:::::::::::::::::::::::::::::::::::::::::::::::::::
PAK can be dangerous in that if you want to run it outside
the current directory you need to run a program called
PAKINST to install it and tell it where it's CNF file is
located. This install program is in the .PAK arc ( ie.
PAK151.ARC or PAK16.ARC ) but it's use is documented in the
back of the docs and many people miss it. PAK can do some
very undesirable things if it is used outside it's home
directory without being installed.. Make sure and run PAKINST
and tell PAK where it's config file is before you use the set
command with ZIPPER and start using it outside of the PAK.EXE
directory..
if you have never, never will, and never want to screw with
PAK.EXE and never see or use PAK files do the following in
your archiver directory pointed to by SPAT..
copy PKUNPAK.EXE PAK.EXE
copy your PK unpacker into a PAK.EXE file.. and change line
one of your ZIPPER.CFG file from " e" to " -e". this will fool
ZIPPER into thinking you have a valid PAK.EXE and if you do
run into a real PAK file ZIPPER will note it as a bad .PAK,
log it and move on..
ZIPPER will abort AFTER the current file being processed if
you press the escape key. It will finish the current file
and then abort cleanly..
ZIPPER sysop version accepts the command line switch b or /b
to run in automated batch mode.. it will require no operator
prompts and will erase all the bad arc files found during the
session at the end. The file badfiles.log will contain all
bad files found and deleted.. this can be used by sysop's to
run EVENTS or unattended conversion sessions.. syntax is..
ZIPPER path/filename /b
or
ZIPPER path/filename b
ie..
ZIPPER d:\arcs\dl1 /b
will convert all ARC and PAK files in directory D:\ARCS\DL1 to
ZIP files and delete any bad arcs or paks found during the
session. The filenames deleted will be in the badfile.log file.